This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
Just in case this helps someone else in a mixed migration environment.
Reloading the SMTP tables and then the Router tables showed a smal line indicating that the Server2 domain could not find an MX record for the legacy Hub1 server. Since this is a new network domain we added the MX record. Got rid of the console error. However, the Legacy Hub1 server rejects external host. Instead of disturbing the production legacy server config with an external host name on SMTP Inbound controls, decided on a different approach.
Server2's configuration had (Router/SMTP Basics) disabled "SMTP used when sending messages outside the local Internet Domain." Then relad the SMTP table and Router. Messages were able to flow using the FOreign SMTP Domain doc and SMTP Connection doc to the 8.5 HubServer. From here , the HubServer has he SMTP connection to the provider's relay.
Feedback response number WEBB7PUV2J created by ~Sigmund Asatoolitflar on 03/05/2009